Packet transmission/reception apparatus and method using forward error correction scheme

ABSTRACT

A packet transmission/reception apparatus and method is provided. The packet transmission method of the present invention includes acquiring a source payload including partial source symbols from a source block, generating a source packet including the source payload and an identifier (ID) of the source payload, generating a repair packet including a repair payload corresponding to the source payload and an ID of the repair payload, generating a Forward Error Correction (FEC) packet block including the source and repair packets, and transmitting the FEC packet block. The source payload ID includes a source payload sequence number incrementing by 1 per source packet. The packet transmission/reception method of the present invention is advantageous in improving error correction capability and network resource utilization efficiency.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of a prior applicationSer. No. 13/777,313, filed on Feb. 26, 2013, which claimed the benefitunder 35 U.S.C. §119(e) of a U.S. Provisional application filed on Feb.27, 2012 in the U.S. Patent and Trademark Office and assigned Ser. No.61/603,438, and under 35 U.S.C. §119(a) of a Korean patent applicationfiled on Oct. 9, 2012 in the Korean Intellectual Property Office andassigned Serial No. 10-2012-0112032, the entire disclosure of each ofwhich is hereby incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a broadcast and/or communicationsystem. More particularly, the present invention relates to a packettransmission/reception apparatus and method in the broadcast and/orcommunication system.

2. Description of the Related Art

With an increase of multimedia contents for user consumption, especiallyhigh capacity multimedia data, such as High Definition (HD) and UltraHigh Definition (UHD) contents, network data congestion has also beenincreasing more and more in broadcast and communication environments. Inthis situation, content data transmitted by a transmitter, such as aHost A, may not be delivered to a receiver, such as a Host B, normally,thus resulting in data loss along a routing path. In many cases, thecontent data are transmitted in units of packets and thus the data lossmay occur in a unit of a packet too. The data loss on the network maycause data packet reception failure of the receiver, and thus, it may bedifficult for the receiver to recover the data carried in the missingpacket. As a consequence, the missing packets may cause audio and videoquality degradation with various deleterious effects, such as a crackedscreen, a missing subtitle, and a file loss, thus, resulting in user'sinconvenience. Accordingly, there is a need of the technique forrecovering the missing data.

One of the well-known missing data recovery techniques is to group datapackets, so-called source packets, with various lengths into a sourceblock and add parity bits or repair packets to the source block thoroughForward Error Correction (FEC) encoding. In the case that there ismissing data, the receiver may be capable of decoding the original datausing the repair information. At this time, the source block may includepackets of contents that use different transmission reliabilities. Ifthe amount of the repair packets is determined according to the packetusing a highest reliability in the source block, then, in the sourceblock, the packets using relatively low reliabilities may beoverprotected so as to degrade the efficiency of the network. Otherwise,if the amount of the repair packets is determined according to thepacket using the lowest reliability in the source block, the packetsusing relatively high reliabilities may not be recovered. Therefore, aneed exists for an error correction method that is capable of improvingerror correction efficiency by dividing the source block. Also, there isa need of a method for protecting the packets using relatively highreliabilities using the parities generated with one or more errorcorrection codes.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present invention.

SUMMARY OF THE INVENTION

Aspects of the present invention are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentinvention is to provide an intra-band signaling method and apparatus fortransmitting/receiving packets in a broadcast and communication system.

Another aspect of the present invention is to provide a method andapparatus for recovering lost packet data efficiently in a broadcast andcommunication system.

Another aspect of the present invention is to provide a datatransmission method and apparatus that may improve an error correctioncapability and network efficiency simultaneously by dividing sourceblocks efficiently in a broadcast and communication system.

Another aspect of the present invention is to provide a datatransmission method and apparatus that may protect the packets needingrelatively high reliability using parities generated with at least oneerror correction code in a broadcast and communication system.

In accordance with an aspect of the present invention, a packettransmission method is provided. The method includes acquiring a sourcepayload that includes source symbols from a source block, generating asource packet that includes the source payload and a source payloadidentifier (ID) of the source payload, generating a repair packet thatincludes a repair payload corresponding to the source payload and arepair payload ID of the repair payload, generating a Forward ErrorCorrection (FEC) packet block including the source packet and the repairpacket, and transmitting the FEC packet block, wherein the sourcepayload ID includes a source payload sequence number that is incrementedby 1 per source packet that is generated.

In accordance with another aspect of the present invention, a packettransmission apparatus is provided. The apparatus includes a ForwardError Correction (FEC) block generator which acquires a source payloadthat includes source symbols from the source block, an FEC packetgenerator which generates both a source packet that includes both thesource payload and a source payload identifier (ID) of the sourcepayload and a repair packet that includes both a repair payloadcorresponding to the source payload and a repair payload ID of therepair payload and which generates a Forward Error Correction (FEC)packet block that includes the source packet and the repair packet, anda transmitter which transmits the FEC packet block, wherein the sourcepayload ID includes a source payload sequence number that is incrementedby 1 per source packet that is generated.

In accordance with another aspect of the present invention, a packetreception method is provided. The method includes receiving a sourcepacket that includes a source payload and a source payload identifier(ID) of the source payload, and receiving a repair packet that includesa repair payload corresponding to the source payload and a repairpayload ID of the repair payload, wherein the source payload ID includesa source payload sequence number that is incremented by 1 per sourcepacket that is generated.

In accordance with still another aspect of the present invention, apacket reception apparatus is provided. The apparatus includes areceiver which receives both a source packet that includes both a sourcepayload and a source payload identifier (ID) of the source payload and arepair packet that includes both a repair payload corresponding to thesource payload and a repair payload ID of the repair payload, whereinthe source payload ID includes a source payload sequence number that isincremented by 1 per source packet that is generated.

Other aspects, advantages, and salient features of the invention willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainexemplary embodiments of the present invention will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a diagram illustrating operations of a transmitter and areceiver of a communication system according to an exemplary embodimentof the present invention;

FIG. 2 is a block diagram illustrating a generation of the FEC encodingblock of the transmitter of FIG. 1 according to an exemplary embodimentof the present invention;

FIGS. 3A and 3B are diagrams illustrating the encoding formats oftwo-stage Forward Error Correction (FEC) encoding scheme for use in apacket transmission/reception method according to an exemplaryembodiment of the present invention;

FIG. 4 is a diagram illustrating generating a source block for applyinga Layer Aware (LA)-FEC in a case of media with two layers in a packettransmission/reception method according to an exemplary embodiment ofthe present invention;

FIG. 5 is a diagram illustrating an information block structure of anFEC block generator according to an exemplary embodiment of the presentinvention;

FIG. 6 is a diagram illustrating an information block structure of anFEC block generator according to another exemplary embodiment of thepresent invention;

FIG. 7 is a diagram illustrating an information block structure of anFEC block generator according to another exemplary embodiment of thepresent invention;

FIGS. 8A and 8B are diagrams illustrating formats of an FEC sourcepacket for use in a packet transmission/reception method according to anexemplary embodiment of the present invention;

FIGS. 9A and 9B are diagrams illustrating formats of a parity packet foruse in a packet transmission/reception method according to an exemplaryembodiment of the present invention;

FIGS. 10 and 11 are diagrams illustrating implementing source and paritypayloads identifiers for use in a packet transmission/reception methodaccording to an exemplary embodiment of the present invention; and

FIGS. 12 and 13 are diagrams illustrating implementing source and paritypayloads identifiers with a two-stage method for use in a packettransmission/reception method according to an exemplary embodiment ofthe present invention.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of exemplaryembodiments of the invention as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the embodiments described hereincan be made without departing from the scope and spirit of theinvention. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of theinvention. Accordingly, it should be apparent to those skilled in theart that the following description of exemplary embodiments of thepresent invention is provided for illustration purpose only and not forthe purpose of limiting the invention as defined by the appended claimsand their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

The exemplary embodiments of the present invention to be described belowdescribe methods for recovering a data packet loss efficiently that maybe applied to a mobile terminal, a Television (TV), a computer, anelectronic slate, a tablet Personal Computer (PC), an electronic book,and any other suitable and/or similar electronic device that may usevarious multimedia services, such as high capacity contents, includingHigh Definition (HD) and Ultra HD (UHD) contents, streaming media, videoconference and/or call services, or any other similar and/or suitablemultimedia service. Particularly, an exemplary embodiment may providemethods for improving decoding performance and transmission efficiencyby generating a source block efficiently with the application of ForwardError Correction (FEC) to the data packets. Although no detaileddescription is made of FEC encoding method herein, the exemplaryembodiments of the present invention may be applied to the systems usinga Reed-Solomon (RS) code, a Low Density Parity Check (LDPC) code, aTurbo code, a Raptor code, a RaptorQ code, an XOR such as a SingleParity-Check Code, a Pro-Motion Pictures Experts Group (MPEG) FEC code,and any other similar and/or suitable system.

The terms to be used in the present specification are defined asfollows: an FEC code may be an error correction code for correctingerror or erasure symbol; an FEC frame may be a codeword generated by FECencoding data to be protected and including a parity or repair part; asymbol may be a unit of data, wherein its size, in bits, may be referredto as the symbol size; a Source Symbol may be an unprotected data symbolwhich may be an information part of an FEC frame; an information symbolmay be unprotected data or a padding symbol which is the informationpart of an FEC frame; a codeword may be an FEC frame generated byFEC-decoding of the information symbol; a parity symbol may be a paritysymbol of the FEC frame generated by FEC encoding from the informationsymbol; a Packet may be a transmission unit including a header and apayload; a payload may be a piece of user data which is to betransmitted from the transmitter and which is placed inside of a packet;a packet header may be a header of a packet including a payload; asource payload may be a payload consisting of source symbols; aninformation payload may be a payload consisting of information symbols;a parity payload may be a payload consisting of parity symbols; a sourceblock may be a set of at least one source payload; an information blockmay be a set of at least one information payload; a parity block may bea set of at least one parity payload; an FEC block may be a set ofcodewords or payloads including information blocks and parity blocks; anFEC delivery block may be a set of payloads including source blocks andparity blocks; an FEC packet may be a packet for transmitting an FECblock; a source packet may be a packet for transmitting a source block;a repair packet may be a packet for transmitting a repair block; an FECpacket block may be a set of packets for transmitting FEC transmissionblocks; a Motion Pictures Experts Group (MPEG) Media Transport (MMT) maybe an international standard under development for efficienttransmission of MPEG data; a source flow may be a sequence of sourcepackets or source payloads having a same source flow Identifier (ID); aparity flow may be a sequence of source packets or source payloadshaving a same parity flow ID; an FEC Flow may be a term referringintegrally to a source flow and at least one parity flow generated forprotecting the source flow; a MMT Asset may be a data entity consistingof one or more M units, which may be a data unit for definingcomposition information and transport characteristics; and a MMT Packagemay be a set of one or more MMT assets depending on the supplementaryinformation such as composition information and transportcharacteristics.

FIG. 1 is a diagram illustrating operations of a transmitter and areceiver according of a communication system according to an exemplaryembodiment of the present invention.

Referring to FIG. 1, a transmitter 100 may include a protocol A block101, an FEC encoding block 102, a protocol B block 103, and atransmitter physical layer block 104. The protocol A block 101 mayprocess the transmission data in order to generate a source payload 130for the FEC encoding block 102. The FEC encoding block 102 may generatea source block as a set of source payloads and may perform FEC encodingon the source block in order to generate a parity payload 131 and mayadd an FEC header 132 to the source and parity payloads in order togenerate FEC packets for the protocol B block 103.

At this time, a combination of the source payload and the FEC header maybe referred to as an FEC source packet, and a combination of the paritypayload and the FEC header may be referred to as an FEC parity packet.Although the FEC source packet may be depicted as a data unit acquiredby arranging the FEC header and the source payload sequentially, asshown in FIG. 1, the present invention is not limited thereto, and thearrangement order can be reversed or may be any suitable and/or similararrangement order. Although the FEC encoding block 102 may be interposedbetween the protocol A block 101 and the protocol B block 103, as shownin FIG. 1, the present invention is not limited thereto, and theprotocol A block 101 may also include the FEC encoding block 102. Inthis case, the FEC parity packet may include a protocol header forperforming the function of the protocol A block 101, and the protocol Ablock 101 may include a multiplexer (not shown) for multiplexing thesource and parity packets into a packet flow.

The transmitter physical layer block 104 may convert the FEC packetsinto a signal appropriate for transmission. Although there may bevarious layers between the protocol B block 103 and the transmitterphysical layer block 104, a detailed description thereof is omittedherein, for the sake of brevity.

A receiver 110 may include a receiver physical layer block 111, aprotocol B block 112, an FEC decoding block 113, and a protocol A block114. The receiver physical layer block 111 may interpret a signalreceived over a transmission channel 120 and may transfer the signal tothe protocol B block 112. Like the transmitter 100, there may be variouslayers between the protocol B block 112 and the receiver physical layerblock 111, however, a detailed description thereof is omitted herein forthe sake of brevity. The protocol B block 112 may transfer the FECpackets acquired by interpreting the received signal or packet to theFEC decoding block 113. At this time, a part of the FEC packetstransmitted by the transmitter may be lost due to network congestionand/or an error occurring at the physical layer such that the FECpackets may not be delivered to the FEC decoding block 113. The FECdecoding block 113 may perform FEC decoding on the received FEC packetsin order to recover the lost source payloads and may deliver therecovered payloads to the protocol A block 114 along with the receivedpayloads.

FIG. 2 is a block diagram illustrating a generation of the FEC encodingblock of the transmitter of FIG. 1 according to an exemplary embodimentof the present invention.

Referring to FIG. 2, the FEC encoding block 102 illustrated in FIG. 1may be implemented as an MPEG MMT FECFRAME 102. The MMT FECFRAME 102 maybe a logical/physical component for generating an FEC flow. Accordingly,if at least two FEC flows are managed at the transmitter 100, then thelogical FECFRAMEs, a number of which may correspond to as many of theFEC flows that are activated independently, and the physical FECFRAMEmay be shared with time sharing. The MMT FECFRAME 102 may receive theinputs of a FEC transmission information and a source payload and mayoutput Out-band signal and a FEC packet block. Although FIG. 2 shows theFEC transport information is input to a controller 210 and an FEC blockgenerator 220, the present invention is not limited thereto, and otherfunction blocks may recognize and use the FEC transport information forother operations.

The MMT standard adopts a two-stage method for protecting packetsneeding relatively high reliability using at least one error correctioncode. In the two-stage method, the MMT FECFRAME 102 may sort apredetermined number of symbols into M first source symbols, wherein Mis an integer equal to or greater than 1, and adds first repair symbolsgenerated through a first FEC encoding to the first source symbols inorder to generate first encoding symbols. Next, the MMT FECFRAME 102 mayadd second repair symbols, which are generated through a second FECencoding of the M first encoding symbols, as second source symbols inorder to generate second encoding symbols. The first and second FECencodings may be performed with a same error correction code ordifferent error correction codes. Candidate error correction codes maybe any of an RS code, an LDPC code, a Turbo code, a Raptor code, aneXclusive OR (XOR) code, or any other similar and/or suitable candidateerror correction code or combination thereof

FIGS. 3A and 3B are diagrams illustrating the encoding formats oftwo-stage FEC encoding scheme for use in a packet transmission/receptionmethod according to an exemplary embodiment of the present invention.

Referring to FIG. 3A, an encoding format in a case where M=1 is shown,and referring to FIG. 3B, an encoding format in a case where M=8 isshown. In order to protect the media data having a layered structureefficiently, a Layer-Aware (LA)-FEC may be used. The media having alayered structure may include contents encoded using Scalable VideoCoding (SVC) and Multiview Video Coding (MVC).

FIG. 4 is a diagram illustrating generating a source block for applyinga LA-FEC in a case of a media with two layers in a packettransmission/reception method according to an exemplary embodiment ofthe present invention.

Referring to FIG. 4, a Base Representation (BR) may refer to data thatis independently decodable at a media codec, and EnhancementRepresentation 1 (ER1) may refer to the data depending on the BR. It isnoted that the BR may be used along with the ER1 in generating a parityfor ER1, as shown in FIG. 4.

Returning to FIG. 2, the controller 210 may generate controlinformation, In-band signals, and Out-band signals using the input ofthe FEC transport information. The In-band signals may be controlinformation that is transmitted as a part of the FEC packet, and theOut-band signals may be the control information transmitted through aseparate packet, protocol, or channel. The FEC transport information maybe processed by a separate controller (not shown), which is not includedin the MMT FECFRAME 102, without involvement of the controller 210 andmay then be input into the FEC block generator 220 and a FEC packetgenerator 240. In this case, the controller 210 may be omitted, whichrespect to the block diagram of FIG. 2.

The control information may include the control information needed forgenerating the FEC block at the FEC encoder 230. A specific FEC codeuses an initial value of a random generator for a parity generationprocedure. At this time, a sequence number assigned to the sourcepayload at a higher layer may use the initial value of the randomgenerator frequently. In this case, since it may be inefficient toextract a necessary value by analyzing, at the MMT FECFRAME 102, thepayload structure of the higher layer by taking notice of the data flow,the identification number may be input to the MME FECFRAME 102 ascontrol information and may be used as the control information of theFEC code, but may not be output as the In-band signal or the Out-bandsignal. The FEC transport information may include transportcharacteristics of the MMT asset and changes depending on theapplication or protocol including the MMT FECFRAME 102.

Referring to FIG. 2, the FEC block generator 220 may receive the sourcepayload and control information as input and may then output the paritypayload, the source payload ID, and the parity payload ID. In order toacquire the parity payload, the FEC block generator 220 may group thesource payloads into a source block and may processes the source blockin order to generate an information block, which may be composed ofinformation payloads having a same length, that are provided to the FECencoder 230. The source payload identifier and parity payload identifierare the identification information needed for identifying differentpayloads. The source payload identifier may be omitted when there isidentification information for identifying the source payload in thelayer or next-order layer including the MMT FECFRAME 102. The sourcepayload identifier and parity payload identifier may be used as input ofthe FEC encoder 230 according to the implementation of the FEC encoder.

FIG. 5 is a diagram illustrating an information block structure of anFEC block generator according to an exemplary embodiment of the presentinvention.

Referring to FIG. 5, the FEC block generator 220 illustrated in FIG. 2may receive 8 source payloads, SPL#0 to SPL#7, having variable packetsize, as an input. The FEC block generator 220 may generate theinformation block composed of 8 information payloads, IPL#0 to IPL#7,acquired by adding padding data to the payloads in order to make thepayload sizes equal to a maximum length S_(max). Although the exemplaryembodiment of FIG. 4 is directed to the case where the maximum lengthS_(max) of the source payload and a length of the information payloadare equal to each other, the present invention is not limited thereto,and the length of the information payload may be set to a value lessthan S_(max) according to a system complexity and memory requirement.

FIG. 6 is a diagram illustrating an information block structure of anFEC block generator according to another exemplary embodiment of thepresent invention.

Referring to FIG. 6, the FEC block generator 220 illustrated in FIG. 2may receive 6 source payloads, SPL#0 to SPL#5, having variable packetsize as an input. The FEC block generator 220 may arrange the payloadsin sequence and divides the sequence by the maximum length S_(max) inorder to generate the information block composed of 5 informationpayloads IPL#0 to IPL#4. It is noted that the last information payloadmay include padding data. According to the exemplary embodiment of FIG.6, since the source block boundaries and the information payloadboundaries do not match with each other, there may be a need to includeinformation, such as source payload length, that is needed forextracting a source payload from the information block, or there may bea need to notify the receiver of the information using a separatemethod. Although the exemplary embodiment of FIG. 6 is directed to thecase where the maximum length S_(max) of the source payload and thelength of the information payload are equal to each other, the presentinvention is not limited thereto, and the length of the informationpayload may be set to a value less than S_(max) according to a systemcomplexity and memory requirement.

FIG. 7 is a diagram illustrating an information block structure of anFEC block generator according to another exemplary embodiment of thepresent invention.

Referring to FIG. 7, the FEC block generator 220 illustrated in FIG. 2may sort a 2-dimensional array having a symbol size of T into m regionsaccording to columns of the 2-dimensional array. FIG. 7 shows a casewhere m=4. If T is not an integer of m, each region may be divided intoregions composed of [T/m]+1 columns and regions composed of [T/m]columns, wherein for any value of a real number X, [X] denotes a maximuminteger that is equal to or less than X. A number of columns of eachregion may be determined through pre-negotiation between the transmitterand the receiver or by enumerating the number of columns of each region.For example, if a remainder of dividing T by m is n, wherein n<m, then afirst region of n may be divided into [T/m]+1 columns and a region ofm-n may be divided into [T/m] columns. However, the present invention isnot limited thereto, and in addition to the above regular regiondistribution, the number of columns constituting each region may bedetermined differently through negotiation between the transmitter andthe receiver or by any similar and/or suitable means.

If needed, a User Datagram Protocol (UDP) Flow ID 701 and a sourcepayload length information 702 may be added to the source payload. Thesource payloads to which the UDP Flow ID 701 and the source payloadlength information 702 are added are arranged from a first row and afirst column without exceeding a symbol size of T. At this time, a spacethat remains empty after arranging the last data of the source payloadin the last row, in which a certain source payload having thesupplementary information has been arranged, is filled or configuredwith predetermined values. Although the predetermined values may bezeros, the present invention is not limited thereto, and thepredetermined values may be any similar and/or suitable values. Forexample, the last data of the first source payload may be arranged inthe second region from among the 4 regions, and then a remaining part705 of the second region may be padded with 0s.

After the source payload having the supplementary information has beenarranged, a next source payload may be arranged from a start point of anext region following the region in which the last row data of theprevious source payload has been arranged. That is, all source payloadsare arranged from a start point of any region. For example, the secondsource payload may be arranged from the start point of the third regionfollowing the zero padding of the remaining part 705 in FIG. 7. If azero padding 704 of the fourth source payload is placed at an end of thefourth region, then a fifth source payload may start at a beginning ofthe next row of the first region. The given source payloads may bearranged in order to generate the information block. In a case of usingplural information block generation schemes, like the MMT system, theremay be a need to send the receiver an identifier, such as ibg_mode,indicating the information block generation scheme.

In a case of using the two-stage method, the information blockgeneration procedure may be performed as follows. In such a case, asource block may consist of M sub-blocks. The source payload of thefirst one of the sub-blocks may be used to generate the firstinformation sub-block which may be transferred to the FEC encoder 230.The FEC encoder 230 may generate a parity payload using the informationsub-block and may transfer the parity payload to the FEC block generator220. This procedure may be performed repeatedly for the second to M^(th)sub-block. When the parity payloads of all sub-blocks are generated,then the first to M^(th) information sub-blocks may be combined into aninformation block, which may be transferred to the FEC encoder 230. TheFEC encoder 230 may generate a parity payload using the informationblock and may transfer the parity payload to the FEC block generator220. Next, the parity payloads generated from the M informationsub-blocks and the parity payload generated from the information blockmay be transferred to the packet generator 240.

In the case of using the LA-FEC method, the information block generationprocedure is performed as follows. In such a case, the media may have Mlayers and the i^(th) layer may depend on the 1, 2, . . . , (i−1)^(th)layers. At this time, the source block may consist of M sub-blocks, andthe ith sub-block may correspond to the data of the i^(th) layer. Thefirst information sub-block may be generate using the source payload ofthe first sub-block and may be transferred to the FEC encoder 230. TheFEC encoder 230 may generate a parity payload using the firstinformation sub-block and may transfer the parity payload to the FECblock generator 220. Afterward, the first information sub-block and thesecond information sub-block are combined into an information blockwhich is transferred to the FEC encoder 230. The FEC encoder 230 maygenerate a parity payload using the information block and may transferthe information block to the FEC block generator 220. This process maybe performed repeatedly in order to combine the first through M^(th)information sub-blocks into an information block, which is transferredto the FEC encoder 230. The FEC encoder 230 may generate the paritypayload using the information block and may transfer the informationblock to the FEC block generator 220. The parity payloads generated fromthe M information sub-blocks and the information block may betransferred to the FEC packet generator 240.

Referring to FIG. 2, the FEC encoder 230 may calculate the paritysymbols using the input of the information block according to apredetermined FEC encoding algorithm and may generate the parity payloadcomposed of the parity symbols, wherein the parity payload is output inthe form of a parity block. According to an exemplary embodiment, theFEC encoding algorithm may calculate a fixed number of parity symbolvalues with the input of a fixed number of information symbols. In thiscase, the FEC encoder 230 may not need extra control information.According to another exemplary embodiment, the FEC encoding algorithmmay request the FEC encoding information according to a relationshipbetween the numbers of information and parity symbols and informationand parity symbols. Although the FEC encoding information may be part ofthe FEC transport information transferred from the FEC block generator220 to the FEC encoder 230, all function blocks of the MMT FECFRAME 102may receive, determine and/or use the FEC transport information asaforementioned.

Referring to FIG. 2, the FEC packet generator 240 may generate an FECpacket including a source or parity payload, a source or parity payloadidentifier, and In-band signals in the form of an FEC packet block.Although the source or parity payload identifier and In-band signals aredepicted separately in FIG. 2, the present invention is not limitedthereto, and the In-band signal may include the source or parity payloadidentifier.

In the MMT system, the source payload may be an MMT Payload Format (PF)or an MMT Transport Packet (TP). The MMT PF may be the output of a D1protocol as the first transport layer of the MMT, and the MMT TP may bethe output of a D2 protocol as the second transport layer of the MMT.The input to the D1 protocol may be a D1 payload. The D1 and D2protocols may have respective headers.

FIGS. 8A and 8B are diagrams illustrating formats of an FEC sourcepacket for use in a packet transmission/reception method according to anexemplary embodiment of the present invention.

Referring to FIG. 8A, a format of an FEC source packet carrying an MMTPF as the source payload is shown. Referring to FIG. 8B, a format of anFEC source packet carrying MMT TP as source payload is shown. In FIGS.8A and 8B, shadowed parts may indicate data, i.e. a source payload,protected by an FEC code. In order to maintain a consistency of theprotocol packet format and a sequential arrangement of the sourcepayloads in the packet, the FEC In-band signals may be arranged in alast part of the FEC source packet. In the case where the source payloadis the MMT PF, the D1 header and payload may be the source payload. Inthe case where the source payload is the MMT TP, then the D2 header, theD1 header and payload may be the source payload. The FEC parity packetsmay carry one or more parity payloads. The parity payload may be usedfor recovering the information block in the format of the MMT PF or theMMT TP.

FIGS. 9A and 9B are diagrams illustrating formats of a parity packet foruse in a packet transmission/reception method according to an exemplaryembodiment of the present invention.

Referring to FIG. 9A, the MMT PF of the source payload is shown.Referring to FIG. 9B, the format of MMT TP of the source payload isshown. In FIGS. 9A and 9B, the shadow parts may indicate the data, suchas a parity payload, that may be used to recover the information block.In FIGS. 9A and 9B, in order for the receiver to acquire the FECinformation quickly, the FEC In-band signal may be arranged between thetransport protocol header and the parity payload. In a case having theMMT TP, the parity payload may be only used for recovering theinformation block in the format of the MMT TP, and thus, the FEC paritypacket of FIG. 9B may have no D1 header. In a case of using thetwo-stage method, the FEC parity packet including the parity payloadgenerated through the first FEC encoding may be referred to as the firstFEC parity packet, and the FEC parity packet including the paritypayload generated through the second FEC encoding may be referred to asthe second FEC parity packet. In a case of the two-stage method, whereinM=1 and the first FEC code has no parity, such a case is identical withthe one stage method, and thus the second FEC parity packets may beregarded as the FEC parity packets.

With respect to the method for generating the source payload identifierand parity payload identifier according to an exemplary embodiment ofthe present invention, certain parameters are defined as follows: k maybe a number of source payloads contained in one source block; M may be anumber of source sub-blocks constituting one source block; k(i) may be anumber of source payloads included in i^(th) source sub-block; S(j) maybe a length of a j^(th) source payload constituting a source flow;S_(max)=max{S(j)}−T may be a length of the information payload;A(j)=ceil (S(j)/T), ceil(x) may be a minimum integer equal to or greaterthan x; K may be a number of information payloads included in aninformation block; K(i) may be a number of information payloads includedin the i^(th) information sub-block; P may be a number of paritypayloads included in a parity block for protecting information; P(i) maybe a number of parity payloads included in the parity block forprotecting the i^(th) information sub-block; B may be a number of paritypayloads included in one parity packet; p may be a number of paritypackets needed for transmitting the parity block generated forprotecting the source block which may be equal to ceil(P/B); and p(i)may be a number of parity packets needed for transmitting the parityblock generated for protecting the i^(th) source sub-block(=ceil(P(i)/B)).

The source payload identifier and the parity payload identifier,according to an exemplary embodiment of the present invention, are shownin tables 1 and 2.

TABLE 1 ESI_SN ESI_SN_Base

TABLE 2 ESI_SN_Base ESI_P IBL PBL

The individual fields of tables 1 and 2 are described below. TheEncoding Symbol ID Sequence Number (ESI_SN) field may denote thesequence number of the information payload included in the sourcepacket. The difference of between respective ESI_SNs of the currentpacket and the next packet may be equal to the number of informationpayloads included in the current packet. The initial value of thesequence number may be set to a value generated randomly and initializedto 0 after reaching a maximum integer value that may be expressed with 2bytes or any other predetermined number of bytes.

The ESI_SN_Base field may be used optionally in the source packet. Ifthe ESI_SN_Base is included in the source packet, then the field is setto a value equal to ESI_SN of the first source packet of the sourceblock to which the packet belongs and corresponds to the boundaryinformation of the source block to which the source packet belongs. Ifthe ESI_SN_Base is included in the first FEC parity packet, then thefield is set to a value equal to ESI_SN of the first source packetincluded in the source sub-block protected by the parity payloadsincluded in the parity packet. If the ESI_SN_Base is included in thesecond FEC parity packet, then the field is set to a value equal toESI_SN of the first source packet included in the source block protectedby the parity payloads included in the parity packet.

The ESI_P field may denote the sequence number of the parity payloadincluded in the parity packet. The ESI_P field may indicate the valueincreasing by 1 from 0 in each parity block and, if one parity packetincludes a plurality of parity payloads, may indicate a minimum valuefrom among the sequence numbers of the parity payloads.

The IBL field may denote the number of information payloads included inthe information (sub-) block protected by the parity payload(s) in theparity packet.

The PBL field may denote the number of parity payloads constituting aparity block corresponding to the parity payload(s) including paritypacket. The PBL field may not be required according to thecharacteristic of the FEC code. In further detail, the PBL flied may notbe needed for the fountain code, which is logically capable ofgenerating parity payloads infinitely, and the PBL field may be neededfor the normal (N, K) block codes.

FIGS. 10 and 11 are diagrams illustrating implementing source and paritypayloads identifiers for use in a packet transmission/reception methodaccording to an exemplary embodiment of the present invention.

Referring to FIG. 10, an exemplary case of using the fountain code isshown. Referring to FIG. 11, an exemplary case of using a block code isshown. In the exemplary embodiment of FIG. 10, P may be omitted in theparity payload identifier of FIG. 10.

FIGS. 12 and 13 are diagrams illustrating implementing source and paritypayloads identifiers with a two-stage method for use in a packettransmission/reception method according to an exemplary embodiment ofthe present invention.

Referring to FIG. 12, an exemplary case of using the fountain code isshown. Referring to FIG. 13, an exemplary case of using the block codeshown. In the exemplary embodiment of FIG. 12, P may be omitted in theparity payload identifier.

Rules for generating respective fields are similarly applied to theexemplary embodiments of FIGS. 10, 11, 12, and 13. The rules are asfollows:

ESI_SN=RN if j=0, otherwise ESI_SN_pre+A(j−1), wherein RN is a randomnumber or 0 and ESI_SN_pre is ESI_SN of the previous Source Packet;

ESI_SN=ESI_SN of the first Source Payload of the Source/Sub-Blockassociated with the Parity Block which includes the FEC Parity Packet;

ESI_P=r*B, wherein r=0, 1, 2, . . . , p−1; and

IBL=K(i) if the Parity Block which includes the FEC Parity Packet is forthe i^(th) Sub-Block of the Source Block, otherwise K; PBL=P(i) if theParity Block which includes the FEC Parity Packet is for the i^(th)Sub-Block of the Source Block, otherwise P.

In the previous exemplary embodiments, the FEC identifier is shown to bearranged at the end of the FEC packet. However, the present invention isnot limited thereto. For example, the FEC identifier of FEC paritypacket may be arranged at the beginning of the FEC packet, while the FECidentifier of the FEC source packet may be arranged at the end, in theFEC packet. Also, both the FEC identifiers may be arranged at thebeginning of the FEC packet. Although not depicted in the previousexemplary embodiments, the FEC Payload ID format may include the FECFlow Identifier too. In a case where no FEC is applied, the non-FECapplication may be notified through Out-bound signaling, wherein the FECflow identifier may be not needed. Accordingly, when the FEC is appliedto all of the source flows, the FEC application may be notified throughthe Out-band signaling while the FEC flow identifies may be transmittedin the FEC identifier format though the In-band signaling. If the FEC isnot applied to all source flows, then the source payload header or thelower layer protocol header may include an FEC flag in order to indicatea presence or absence of the FEC payload identifier and, if the FECpayload identifier is present, then the FEC payload identifier may betransmitted along with the FEC flow identifier. In this case, thereceiver may sort the FEC packets by FEC flow identifier from the FECpayload identifier and may decode a corresponding FEC block in the FECpacket blocks having the same FEC flow identifier in order to recoverthe lost source payload.

A description is made of the FEC encoding procedure of the transmitteraccording to the present exemplary embodiment hereinafter. Thetransmitter may segment the media content to be transmitted into sourcepayloads in order to generate a sequence of source payloads and maydifferentiate among the source flows according to whether the FECprotection is applied, an FEC type to be applied, an FEC codingstructure, and a media characteristic or a Quality of Service (QoS),such as lossy or lossless QoS, in order to assign an appropriate FlowIdentifier. The FEC flow identifier of each source flow may be stored ina packet carrying the source flow to be notified to the receiver. Forexample, if an FEC flow identifier=0, then this may indicate that theFEC protection is not applied and, otherwise if an FEC flowidentifier≠0, then this may indicate that the FEC protection is applied.However, the present invention is not limited thereto, and an FECprotection scheme may be applied according to any similar and/orsuitable manner.

The transmitter may send the receiver the information on whether toapply the FEC protection, the applied FEC type, the FEC codingstructure, an Information Payload Size T, an ibg_mode, or any othersimilar and/or suitable characteristic, through Out-band signaling.Accordingly, the receiver may acquire the information using the FEC flowidentifier. The transmitter may transmit the information using a SessionDescription Protocol in a Session Setup procedure or using a specificpacket other than the FEC packet.

The transmitter may apply the FEC encoding indicated by the FEC flowidentifier to the corresponding source flow. For this purpose, thetransmitter may divide the source flow into source blocks. Thetransmitter may convert the source block into the information block orsub-block according to the FEC coding structure, which may be a onestage or a two stages structure, and an ibg_mode. The transmitter maygenerate the parity block(s) from the information block or sub-blockusing a respective FEC code. The transmitter may generate the FEC packetblock for transmitting the source block and the generated parity block,and each FEC packet may include the information on FEC flow identifier,the FEC payload identifier, and the payload type. The transmitter mayuse the payload type information to determine whether the correspondingFEC packet is a source packet or a parity packet. When the two-stage FECcoding is applied, the transmitter may discriminate between the parity 1and parity 2. The transmitter may transmit the FEC packet block throughthe network.

A description is made of the FEC decoding procedure of a receiveraccording to the present exemplary embodiment hereinafter. The receivermay determine the FEC flow identifier of each source flow, whether FECprotection is applied or not, the FEC type, the FEC coding structure,the information payload size T, the ibg_mode, and other similarparameters that are transmitted by the transmitter through the out-bandsignaling and may prepare for FEC decoding. The receiver may sort thereceived FEC packets according to an FEC flow identifier. The receiverdetermines whether the corresponding FEC packet is the FEC source packetor FEC parity packet according to the payload type information in theFEC packet sorted by the FEC flow identifier. In the case that thetwo-stage FEC coding is applied, the receiver may determine whether therec parity packet is the parity 1 or parity 2. If the corresponding FECpacket is the FEC source packet, the receiver may determine the ESI_SNfrom the source FEC payload ID and, otherwise if the corresponding FECpacket is the parity FEC packet, the receiver may determine theESI_SN_Base, the ESI_P, IBL, the PBL, or other similar parameters, fromthe source FEC payload ID. The receiver may arrange the informationblock or parity block corresponding to the payloads, which may be one ofa source or a parity payload, of the FEC packet according to thedetermined FEC payload ID and the previously recognized informationpayload size T and ibg_mode at the correct position in order to generatethe FEC block for FEC decoding. The receiver may perform decoding withthe FEC code applied to the generated FEC block in order to recover theinformation payload corresponding to the lost source payload duringtransmission. If padding data are added to the recovered informationpayloads, then the receiver may remove the padding data in order tofinally recover the source payloads. If the information block generationscheme, as depicted in the exemplary embodiment of FIG. 5, is used andif the source payload length fields are configured to be separate fromthe FEC block, the receiver may decode the FEC block for the lengthfield in order to know the length of each payload and in order to removethe padding data from the recovered information payload.

According to another exemplary embodiment, the fields of tables 1 and 2are defined as follows:—

ESI_SN=RN if j=0, otherwise ESI_SN_pre+A(j−1), wherein RN is a randomnumber or 0 and ESI_SN_pre is ESI_SN of the previous Source Packet;

ESI_SN_Base=ESI_SN of the first Source Payload of Source Block whichincludes the FEC Source Packet;

ESI_SN=ESI_SN of the first Source Payload of Source/Sub-Block associatedwith the Parity Block which includes the FEC Parity Packet;

ESI_P=r*B, wherein r=0, 1, 2, . . . , p−1;

IBL=K(i) if the Parity Block which includes the FEC Parity Packet is forthe ith Sub-Block of the Source Block, otherwise K; and

PBL=P(i) if the Parity Block which includes the FEC Parity Packet is forith Sub-Block of the Source Block, otherwise P.

In the case of using the information block generation method of FIG. 6,the following field may be included in the FEC parity payloadidentifier: SBL may be a number of source payloads included in thesource block or sub-block protecting the parity payload belonging to theparity packet.

In the case of using the information block generation method of FIG. 7,there may be, in the information payload corresponding to the sequencenumber, a need for the information indicating the start position of thesource payload included in the source packet along with the sequencenumber of the information payload. The information block of FIG. 7 mayinclude 6 source payloads. At this time, the sequence number may beassigned in the form of (0, 0), (1, 2), (6, 1), (10, 0), and (12, 1),which are row-start region pairs. According to another exemplaryembodiment, the sequence number may assigned in units of informationpayload with the start point of the source payload of 0, 6 which isequal to 1*4+2, 15 which is equal to 3*4+3, 25 which is equal to 6*4+1,40 which is equal to 10*4, and 49 which is equal to 12*4+1.

The source payload identifier and the parity payload identifier,according to another exemplary embodiment of the present invention, areshown in Tables 3 and 4.

TABLE 3 SB_ID IP_ID_SB SSB_ID IP_ID_SSB

The individual fields of Table 3 may denote the following: a SourceBlock IDentifier (SB_ID) may be an identifier of the source block towhich the source payload included in the source packet belongs; anInformation Payload IDentifier within a Source Block (IP_ID_SB) may bean identifier of the information payload included in the packetcorresponding to the information block generated from the source blockindicated by the SB_ID; a Source Sub-Block IDentifier (SSB_ID) may be anidentifier of the source sub-block to which the source payload includedin the source packet belongs, wherein the SSB_ID field may be includedonly when the two-stage method is used; and an Information PayloadIDentifier within a Source Sub-Block (IP_ID_SSB) may be an identifier ofthe information payload included in the packet corresponding to theinformation sub-block generated by converting the source sub-blockindicated by the SSB_ID, wherein the IP_ID_SSB field may be includedonly when the two-stage method is used.

TABLE 4 SB_ID (SSB_ID) PP_ID IBL (ISBL) PBL

The individual fields of table 4 may denote the following. An SB_ID orSSB_ID may be an identifier of a source block or source sub-blockprotected by the parity block including the parity payload carried inthe parity packet. The SSB_ID may be assigned to the first FEC paritypacket, and the SB_ID is assigned to the second FEC parity packet. AParity Payload IDentifier (PP_ID) may be an identifier of the paritypayload in the parity block to which the parity payload carried by theparity packet belongs. An Information Block Length (IBL) or anInformation Sub-Block Length (ISBL) may be a number of informationpayloads included in the information block or information sub-blockprotected by the parity block to which the parity payload carried in theparity packet belongs. The IBL may be assigned to the first FEC paritypacket, and the ISBL may be assigned to the second FEC parity packet. AParity Block Length(PBL) may be a number of parity payloads included inthe parity block to which the parity payload carried in the paritypacket belongs.

In the case of using the one stage method, the individual fields of theFEC payload identifier of Tables 3 and 4 may be generated as follows.Typically, the SB_ID may increase by 1 from a certain value that is inthe range of integers expressible with 2 bytes. The SB_ID may beinitialized to 0 after reaching the maximum expressible value. TheIP_ID_SB may increase from 0 by 1 per information payload in each sourceblock. In the case of using the information block generation method ofFIG. 7, the IP_ID_SB may increase by 1 per segmented informationpayload. In the case of the information block shown in FIG. 7, theIP_ID_SB field of each FEC source payload identifier is 0, 6, 15, 25,40, and 49 as described according to the above-described exemplaryembodiment. The PP_ID may increase from 0 by 1 per parity payload ineach parity block. Typically, the IP_ID_SB and the PP_ID are values thatare in the range of integer values expressible with 2 bytes, that isvalues that are less than 64000. The values associated with the payloadof a specific FEC packet may be carried at a part of the FEC paritypayload, but the maximum values of the IBL and the PBL may betransmitted in the form of the FEC Out-band signal.

In a case where the two-stage method is used, the individual fields ofthe FEC payload identifier of Tables 3 and 4 may be generated asfollows. Typically, the SB_ID may increase by 1 from a certain valuethat is in the range of integers expressible with 2 bytes. The SB_ID maybe initialized to 0 after reaching the maximum expressible value. TheIP_ID_SB may increase from 0 by 1 per information payload in each sourceblock. The SSB_ID may be a positive integer starting from 0 in eachsource block and increases by 1 per source sub-block of a respectivesource block. In the case of using the information block generationmethod of FIG. 7, the IP_ID_SB and IP_ID_SSB may increase by 1 persegmented information payload. The PP_ID may increase from 0 by 1 perparity payload in each parity block. Typically, the IP_ID_SB, theIP_ID_SSB, and the PP_ID may be values in the range of integer valuesexpressible with 2 bytes.

As described below, the FEC source payload identifier generation rulesare described with respect to the case of using the two-step method withreference to the case where the source block is divided into two sourcesub-blocks, wherein each source sub-block includes two source payloads.For the purpose of convenience, it may be assumed that the sourcepayload and the information payload have a 1:1 relationship. At thistime, the FEC source payload identifiers SB_ID, IP_ID_SB, SSB_ID, andIP_ID_SSB of the source packets SP#0, SP#1, . . . , SP#15 are asfollows.

SP#0: (0, 0, 0, 0)

SP#1: (0, 1, 0, 1)

SP#2: (0, 2, 1, 0)

SP#3: (0, 3, 1, 1)

SP#4: (1, 0, 0, 0)

SP#5: (1, 1, 0, 1)

SP#6: (1, 2, 1, 0)

SP#7: (1, 3, 1, 1)

At this time, assuming that the number of source sub-blocks per sourceblock M is 2 and is transferred to the receiver through the Out-bandsignal, then the SB_ID and the SSB_ID fields may be replaced with aBlock Identifier (B_ID) field. The B_ID may start at 0 and may increaseby 1 per source sub-block. The B_ID may be initialized to 0 afterreaching the maximum value expressible with 2 bytes. At this time, theSB_ID=floor (B_ID/M), and the SSB_ID=B_ID−M*SB_ID. The function of floor(X) may denotes a maximum integer not exceeding a value of X. In anexemplary case where the source block is divided into two sourcesub-blocks that each include two source payloads, the SB_ID, theIP_ID_SB, the SSB_ID, and the IP_ID_SSB corresponding to FEC sourcepayload identifiers of B_ID, IP_ID_SB, and IP_ID_SSB of the sourcepackets SP#0, SP#1, . . . , SP#7 are as follows.

SP#0: (0, 0, 0)=>(0, 0, 0, 0)

SP#1: (0, 1, 1)=>(0, 1, 0, 1)

SP#2: (1, 2, 0)=>(0, 2, 1, 0)

SP#3: (1, 3, 1)=>(0, 3, 1, 1)

SP#4: (2, 0, 0)=>(1, 0, 0, 0)

SP#5: (2, 1, 1)=>(1, 1, 0, 1)

SP#6: (3, 2, 0)=>(1, 2, 1, 0)

SP#7: (3, 3, 1)=>(1, 3, 1, 1)

In the case of using the two-stage method, the FEC parity payloadidentifier may be identical with the FEC parity payload of the caseusing the one stage method, with the exception that the unit ofinformation to be protected by the parity packet may be the informationsub-block or information block depending on whether the parity packetincluding the FEC parity payload identifier is the first FEC paritypacket or the second parity packet.

In the case of using the two-stage method or the LA-FEC, the jointdecoding of the first and second decoders may become possible accordingto the FEC code design. In the case of using the joint decoding, boththe IBL and PBL of each code may need to be secured. In the abovedescribed exemplary embodiment, the IBL and the PBL may be acquired byreceiving only one parity packet for the corresponding FEC block.However, if the channel condition deteriorates, a specific FEC blockreception failure may occur. In this case, it may not be possible torecover the information block through joint decoding logically, however,if the IBL and the PBL are not acquired, the situation may become worseif the decoding is not performed. Accordingly, in order to overcome thissituation, the IBL and the PBL values may be transmitted through anextra FEC Out-band signal, as shown in Table 5. If M is included in theFEC transport information, an M field may be omitted in Table 5.Furthermore, since the IBL is the sum of all ISBL values, the IBL mayalso be omitted from Table 5.

TABLE 5 M For i = 1 to M ISBL for the i-th SSB PBL for the i-th SSB Endfor IBL PBL

A description is made of the exemplary Out-band signal for the jointdecoding of the two-step method with the assistance of the case wherethe source block is divided into two source sub-blocks, wherein eachsource sub-block includes two source payloads, and with the first FECcode generating a one parity payload per source sub-block and the secondFEC code generating a two parity payload per source block. The Out-bandsignal in the format of Table 5 may be structured as shown in Table 6.

TABLE 6 Value Description 2 Number of source sub-blocks per source block2 Number of payloads of first information sub-block 1 Number of payloadsof parity block protecting first information sub-block 2 Number ofpayloads of second information sub-block 1 Number of payloads of parityblock protecting second information sub-block 4 Number of payloads ofinformation block 2 Number of payloads of parity block protectinginformation block

Since the entire or partial control information may be transmittedperiodically or the entire or partial FEC configuration information maybe transmitted through the In-band signaling of the present exemplaryembodiments, a receiver may acquire the FEC configuration information inthe contemporaneous service and may perform FEC decoding in order torecover the lost data, thus, providing an improvement of servicequality.

As described above, the packet transmission/reception method of thepresent invention may improve error correction capability and networkresource utilization efficiency.

It will be understood that each block of the flowchart illustrationsand/or block diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions that may be implemented and/or executed onhardware. These computer program instructions may be provided to aprocessor of a general purpose computer, a special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, are an apparatus forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer program instructions may also bestored in a non-transitory computer-readable memory that can direct acomputer or other programmable data processing apparatus to function ina particular manner, such that the instructions stored in thenon-transitory computer-readable memory produce an article ofmanufacture including instruction means which implement the functionand/or act specified in the flowchart and/or block diagram block orblocks. The computer program instructions may also be loaded onto acomputer or other programmable data processing apparatus to cause aseries of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer implemented process suchthat the instructions which execute on the computer or otherprogrammable apparatus provide steps for implementing the functionsand/or acts specified in the flowchart and/or block diagram block orblocks.

Furthermore, the respective block diagrams may illustrate parts ofmodules, segments or codes, including at least one or more executableinstructions for performing at least one specific logic function.Moreover, it should be noted that the functions of the blocks may beperformed in different order in several modifications. For example, twosuccessive blocks may be performed substantially at the same time, ormay be performed in reverse order according to their functions.

The term “module” according to the exemplary embodiments of theinvention, means, but is not limited to, a software or hardwarecomponent, such as a Field Programmable Gate Array (FPGA), anApplication Specific Integrated Circuit (ASIC), or any other similarand/or suitable software or hardware component which performs certaintasks. A module may be configured to reside on an addressable storagemedium and may be configured to be executed on one or more processors.Thus, a module may include, by way of example, components, such assoftware components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables. The functionality provided for in the components andmodules may be combined into fewer components and modules or furtherseparated into additional components and modules. In addition, thecomponents and modules may be implemented such that they execute one ormore CPUs in a device or a secure multimedia card.

While the invention has been shown and described with reference tocertain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the invention asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A packet transmission method comprising:identifying a mode of source packet block generation; generating asource packet block that includes at least one source packet, a sourcepacket including a source payload and a source payload identifier (ID)of the source payload; generating a repair packet block that includes atleast one repair packet, a repair packet including a repair payloadcorresponding to at least one source payload and a repair payload ID ofthe repair payload; and transmitting the repair packet block, andwherein the source payload ID includes a source payload sequence numberthat starts from an arbitrary value and is initialized to 0 afterreaching a maximum value, and wherein the mode of source packet blockgeneration provides information on a size of the source payload.
 2. Thepacket transmission method of claim 1, wherein the source payload ID andthe repair payload ID are generated based on the mode of source packetblock generation.
 3. The packet transmission method of claim 1, whereinthe repair payload ID comprises an initial sequence number indicatingthe source payload sequence number corresponding to a first sourcepayload in the source packet block.
 4. The packet transmission method ofclaim 1, wherein the repair payload ID comprises a repair payload ID foridentifying the repair payload of the repair packet, and wherein therepair payload ID starts at 0 and is incremented by 1 with each repairpayload in the repair packet block.
 5. The packet transmission method ofclaim 1, wherein the repair payload ID comprises a repair payload lengthindicator indicating a number of repair payload in the repair packetblock.
 6. The packet transmission method of claim 1, wherein the repairpayload ID comprises a source payload length indicator indicating anumber of source payloads included in the source packet block.
 7. Apacket transmission apparatus, the apparatus comprising: a transmitterfor transmitting a repair packet block; and a controller for controllinga packet generator for identifying a mode of source packet blockgeneration, for generating a source packet block that includes at leastone source packet, a source packet including a source payload and asource payload identifier (ID) of the source payload, and generating therepair packet block that includes at least one repair packet, a repairpacket including a repair payload corresponding to at least one sourcepayload and a repair payload ID of the repair payload, wherein thesource payload ID includes a source payload sequence number that startsfrom an arbitrary value and is initialized to 0 after reaching a maximumvalue, and wherein the mode of source packet block generation providesinformation on a size of the source payload.
 8. The packet transmissionapparatus of claim 7, wherein the source payload ID and the repairpayload ID are generated based on the mode of source packet blockgeneration.
 9. The packet transmission apparatus of claim 7, wherein therepair payload ID comprises an initial sequence number indicating thesource payload sequence number corresponding to a first source payloadin the source packet block.
 10. The packet transmission apparatus ofclaim 7, wherein the repair payload ID comprises a repair payload ID foridentifying the repair payload of the repair packet, and wherein therepair payload ID starts at 0 and is incremented by 1 with each repairpayload in the repair packet block.
 11. The packet transmissionapparatus of claim 7, wherein the repair payload ID comprises a repairpayload length indicator indicating a number of repair payloads includedin the repair packet block.
 12. The packet transmission apparatus ofclaim 7, wherein the repair payload ID comprises a source payload lengthindicator indicating a number of source payloads included in the sourcepacket block.